Correlating genealogy records systems and methods

ABSTRACT

A method of consolidating genealogy records includes partitioning the records using at least one index file to form one or more partitions, sorting the records in a partition based on a data element in the records, comparing records within a sort range, based on the comparison, identifying same person records, consolidating information in the same person records, receiving a request from a user to view at least a portion of the consolidated information for a particular group of same person records, and sending a file that includes the portion to the user.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is related to co-pending, commonly assigned andconcurrently filed U.S. patent application Ser. No. 10/748,441,entitled, “GENEALOGY INVESTIGATION AND DOCUMENTATION SYSTEMS ANDMETHODS”, by Bennett Cookson, Jr., et al., and to co-pending, commonlyassigned and concurrently filed U.S. patent application Ser. No.10/748,442, entitled, “PROVIDING ALTERNATIVES WITHIN A FAMILY TREESYSTEMS AND METHODS”, by Bennett Cookson, Jr., et al., the entiredisclosure of each of which is herein incorporated by reference for allpurposes.

BACKGROUND OF THE INVENTION

The present invention relates generally to genealogy and moreparticularly to computer-based genealogy investigation tools.

Genealogy is an enjoyable hobby to some and an important life's work tomany. Whether for cultural, religious, recreational or other reasons,many people wish to trace their ancestry.

The process of genealogy investigation has evolved considerably over theyears. In the past, the practice involved keeping notes in family bibleshanded down through the generations, and many continue to do this today.Not very long ago, the process often required traveling to the hometownsof ancestors to pore over public records, newspapers, and the like atcourthouses, libraries, and such. Once found, family information waswritten into journals and notebooks or onto index cards. Because of thegeometric expansion of information with each generation, analyzing theinformation became a daunting task. The advent of computers, however,has created significant opportunities for improving and simplifying theprocess.

Many public records are now accessible using a computer and theInternet, thus allowing investigators to search electronically usingkeywords and such without having to travel to where the original recordsare kept. Additionally, several public and private efforts to collectand catalog genealogy data have resulted in publicly accessibledatabases with much of the work already complete. Further still, somecompanies have produced commercial web sites where individuals cancooperate to extend a common family tree. Some examples of each include:<www.archives.gov>, the US National Archives and Record Administrationwebsite; <www.familysearch.org>, the LDS Church Family Search website;<www.ancestry.com>, the Ancestry.com website, which includes theAncestry World Tree; <www.genealogy.com>, the Genealogy.com website,which (includes the World Family Tree); <www.ellisisland.org>, whichincludes immigration records; <www.interment.net>, which includesCemeteries and Cemetery Records; <www.rootsweb.com>, which includesWorld Connect; <www.onegreatfamily.com>, the One Great Family website;<www.MyTrees.com>; and <www.GenCircles.com>. In fact, the process hasbecome so popular that a standard data format has evolved.

GEDCOM (Genealogical Data Communication) is an industry standard dataformat for genealogical information. It uses a standard ASCII fileformat in which each line contains one data element. [A completedescription of the GEDCOM file format is available at<www.gendex.com/gedcom55/55gcint.htm>, the content of which is entirelyincorporated herein by reference for all purposes.] Many genealogyinvestigation services now collect and distribute data using the GEDCOMstandard.

Despite the technological advances—or in some cases because of thetechnological advances—relating to genealogy, the activity remains ripefor improvement. One significant limitation that exists in many “open”genealogy investigation tools (i.e., those that allow independent usersto submit data), is a bias in favor of the information submitted by themost recent submitter. Because of the way data is related within thesesystems, data conflicts are difficult to resolve. The problem isrectified by allowing the latest submitter to overwrite conflicting datasubmitted by a previous user. This is but one example of the manylimitations of presently-available genealogy investigation tools.Embodiments of the present invention address these and many otherlimitations.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the invention thus provide a method of consolidatinggenealogy records. The method includes partitioning the records using atleast one index file to form one or more partitions, sorting the recordsin a partition based on a data element in the records, comparing recordswithin a sort range, based on the comparison, identifying same personrecords, consolidating information in the same person records, receivinga request from a user to view at least a portion of the consolidatedinformation for a particular group of same person records, and sending afile that includes the portion to the user.

In some embodiments partitioning the records using at least one indexfile includes using a surname index to identify records having the samesurnames and grouping those records into a surname partition. The methodmay include using the surname index to identify records having similarsurnames and grouping those records into the surname partition. Themethod may include using a phonetic algorithm to identify records havingsimilar surnames. The phonetic algorithm may include double metaphoneand/or SOUNDEX. Sorting the records in a partition based on a dataelement in the records may include sorting the records based on birthdate. Sorting also may be based on name, death data, death place, and/orbirth place. Comparing records within a sort range may include comparingrecords within a birth date range. Identifying same person records mayinclude calculating a score that represents the likelihood that a pairof compared records represent the same person. The method may includecomparing records related to pairs of same person records. Comparingrecords related to pairs of same person records may include revising thescore based on the comparison of related records. Identifying sameperson records may include comparing the score to a predeterminedthreshold and rejecting records as “same person” records if the score isbelow the threshold. The portion may include a family tree based onconsolidated information from a plurality of records.

In other embodiments the present invention provides a system forconsolidating genealogy records. The system includes a processorprogrammed to partition the records using at least one index file toform one or more partitions, sort the records in a partition based on adata element in the records, compare records within a sort range, basedon the comparison, identify same person records, consolidate informationin the same person records, receive a request from a user to view atleast a portion of the consolidated information for a particular groupof same person records, and send a file that includes the portion to theuser.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the remaining portions of thespecification and the drawings wherein like reference numerals are usedthroughout the several drawings to refer to similar components. Further,various components of the same type may be distinguished by followingthe reference label by a dash and a second label that distinguishesamong the similar components. If only the first reference label is usedin the specification, the description is applicable to any one of thesimilar components having the same first reference label irrespective ofthe second reference label.

FIG. 1 illustrates a genealogy investigation and documentation systemaccording to embodiments of the invention.

FIG. 2A illustrates a method of genealogy investigation that may beembodied in the system of FIG. 1.

FIG. 2B illustrates one example of the process of relationshipcorrelation in greater detail.

FIG. 2C illustrates an exemplary consolidated person page according toembodiments of the invention.

FIGS. 3A-3Q illustrate a detailed example of a record consolidationprocess according to an embodiment of the invention.

FIGS. 4A-4D illustrate a series of display screens that a user mayencounter when using an embodiment of a system according to the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present invention provide systems and methods forgenealogy investigation. In some embodiments, the present inventioncomprises systems and methods for receiving data from any combination ofa number of sources and storing the data as records in variousstandardized and/or proprietary formats. Records may correspond topersons, either living or deceased, information about the persons, andrelationships among them. In some embodiments, the records are used toproduce family trees, either in response to a request from a user orcontinuously as new data is received. Thus, embodiments of the presentinvention provide systems and methods for taking data identifying aspecific individual from any source and in any format, converting itinto a common format (a persona), identifying what parts of that datamay define relationships with other persons on which data is available,and processing the various data elements (persona) into pedigrees,without regard to whether any of the data elements have been so combinedprior to that processing, whether in GEDCOM or any other family historyformat.

In contrast to previously-known “open” family tree systems, embodimentsof the invention described herein treat new information merely asadditional data. This is the case whether the data comes from randomusers or from highly reliable records systems. No information iscategorically deemed “correct” and thus does not “overwrite” dataprovided by others. Many previously-known systems sufferer from a biasin favor of the most recently submitted data, resulting in confusionwhen two data sources disagree. Those skilled in the art will appreciatethis problem by realizing how different users with access to the sameopen system may alternatively and continuously overwrite each other'sentries, especially if they disagree on some aspect of a family tree ora person.

Also in contrast to previously-known systems, embodiments of theinvention described herein are “data-centric” as opposed to“tree-centric.” This means that embodiments described herein collectinformation and store the information as data records that representtree elements (e.g., nodes and relationships). The elements, however,are not conclusively linked together and the information therein is notdeemed correct, but instead the information is used to inferrelationships and attributes when the likeliness exceeds a threshold. Asa result, new information may either strengthen, diminish, or not affectan existing inference of a relationship or information about a person.Conversely, many previously-known systems collect data using a treestructure. New information is added only by linking off of existingtrees or starting a new tree. The tree structure is the essence of thedata gathering process. If a user adds new information by creating aseemingly incorrect relationship, the situation is corrected only bydissolving the relationship. Once the relationship is dissolved by asubsequent user, the previous user's interpretation of information thatlead to the perceived existence of the relationship is gone.

As used herein, the term “tree” or “family tree” will refer to ahierarchical structure that links generations in parent-childrelationships. It should be understood that a tree may be as simple asone parent and one child or as complex as the theoretical “single familytree” that links all individuals. Thus, any specific tree may be a partof another tree; the two may overlap, or one may completely include theother.

Trees are made up of nodes and relationships. Nodes represent persons,either living or dead. Relationships exist between nodes and representreal life relationships between the persons represented by the nodes.Relationships include mother, father, child, spouse, sibling, self orsame as, and the like.

As used herein, “persona” will be understood to mean an instance of aperson and a “persona record” is a data record of information from asingle source that describes the person. Many different persona recordsmay represent any given persona.

A persona may have one or more “assertions,” which are presumptivetruths about the persona. An assertion (or “inference”) may be an eventsuch as birth, death, draft registration, and the like. An assertionalso may be an attribute such as name, occupation, race, hair color,fingerprint, DNA, and the like. An assertion may become such because anindividual believes it to be true. As will be described, however, anindividual or the system described herein may generate an assertionbased on a review of other information. For example, based on acomparison between records, an inference of a relationship or anattribute may result. Assertions, however, may be rejected by usersand/or may be overcome by new information.

“Primary source” or “primary source data” refers to a source ofnon-compiled genealogy information or the data therefrom. For example, acensus database is a primary source, as is a news paper.

Having described embodiments of the invention generally, attention isdirected to FIG. 1, which illustrates an exemplary system 100 accordingto embodiments of the invention. The system includes a host computingsystem 102 and a network 104 through which the host computing systemcommunicates with user computers 106, tree databases 108, and recordsdatabases 110. The host computing system 102 may include a processingsystem 112, a storage system 114, a web server 116, administrativecomputers 118, and the like. The host computer system 102 includessoftware that programs it to perform the methods described herein.

The various elements than make up the host computing system 102 may beco-located at a single facility or distributed across a geographic area.The processing system 112 of the host computing system 102 may be anysuitable computing device, or combination of devices, that areprogrammable to carry out the functions of embodiments of the presentinvention. Examples include mainframe computers, workstations, servers,personal computers, laptop computers, and the like. The storage system114 may be any storage device or combination of storage devices.Examples include a server, a database, or the like, or any other type ofstorage arrangement, and may include magnetic, optical, solid statememory, and/or the like, or any other type of storage medium. The webserver 116 may be any server capable of providing a web-like interfaceto a network, either internal or external. The administrative computers118 may be any computing devices capable of providing administrativeusers access to the operations of the system.

The network 104 may be wired or wireless, and may include the Internet,a virtual private network, a local area network, a wide area network,and/or the like. The user computers 106 may be any computing devicescapable of accessing the host computing system 102 via the network 104.

The tree databases 108 and records databases 110 may be any storagedevices and/or computing systems mentioned above with respect to thehost computer system. Tree databases 108 and records databases 110 alsomay be non-electronic primary sources. These databases may includepublic records databases, primary sources, commercial genealogydatabases, private databases, and the like. For example, the tree andrecords databases may comprise any of the following: Ancestry WorldTree, Social Security Death Index, World Family Tree, birth certificate,death certificate, marriage certificate, draft registration, veterans,property records, census, motor vehicle, and the like.

Those skilled in the art will appreciate that the foregoing is but oneexample of a system according to the present invention. Other systemsare possible.

Attention is directed to FIG. 2A, which illustrates a first method 200according to embodiments of the invention. The method may be implementedin the system 100 of FIG. 1 or other suitable system. It is to beunderstood that the method 200 is merely exemplary of a number ofequivalent methods according to embodiments of the invention all ofwhich are within the scope of the present invention. Equivalent methodsmay include more, fewer or different steps than those described herein,as is apparent to those skilled in the art in light of this disclosure.

The method 200 begins at block 202 wherein a host computing system, suchas the system 102 described above, receives data. The data includesassertions relating to one or more personas. Assertions may include:first, middle, and last names, name prefixes (Sir, Mr., Dr. Mrs., andthe like) and/or name suffixes (Sr., Jr., III, J. D., and the like);addresses; birth dates; birth places; death dates; death places; spousenames; children names; sibling names; relationships; and the like.

Data may be received in any or a number of forms. For example, data maybe in the form of a family tree or in the form of records representingindividual persons. In some examples, data is received as a GEDCOM file.In other examples, data is taken from indexes of primary source recordssuch as census and vital records. Other examples are possible, includingdata being received in a combination of the aforementioned forms.

Data may be received from any of a number of sources. In some examples,data is received from databases such as the Ancestry World TreeDatabase, the World Family Tree Database, the 1930 Mini-Tree Database,and the like. In other examples, data is received from records databasessuch as birth records databases, death records databases, marriagerecords databases, census records databases, draft card databases, andthe like. In other examples, data is received from individual users aseither trees or individual records. In fact, potential sources includeall census records (federal, state, and local) for any country, usersubmitted family tree data, death indexes such as SSDI for the US orCivil Registration in the UK, newspaper obituaries, various sources andforms of vital records, the Family Data Collection, military andmilitary pension records, and/or any database that has names, dates,places and/or relationships. Other examples are possible, including databeing received from any combination of the foregoing.

At block 204, data is stored as individual records. Records may includepersona records, relationship records, and the like. This processinvolves evaluating the data and standardizing (or normalizing) itsformat. Many examples of this process exist, several of which will bedescribed in more detail hereinafter. Generally, however, each recordrepresents data from a single source and an individual person may berepresented by many different records. Thus, unlike manypreviously-known genealogy investigation tools, embodiments of thepresent invention do not necessarily assume new data to be the mostaccurate data and use it to overwrite existing data. In most embodimentsof the invention, each time data is added, it is stored as at least onenew record. In a specific example, name, birth, birth place, death, anddeath place are stored in a record in an “individual nodes” database,and, if the data indicates a relationship, the related names and therelationship type are stored as a record in an “individual links”database. If the data includes other information, this information isstored in an “other data” database in some embodiments.

At block 206, one or more individual node records are compared. Thecomparison may operate on any or all of the information in the recordsand may use methods know to those skilled in the art or methods that areapparent in light of this disclosure. In some cases, the comparisonincludes factors that account for the reliability of the source. Forexample, public records may be considered more reliable thanuser-submitted data. The comparisons also may include adjustments basedon other records. For example, if a draft registration exists for anindividual, a birth certificate indicating the person was born only fiveyears prior to the registration date is likely not for the same person.Many such factors may be included. In a specific embodiment, eachcomparison between two individual node records results in a factor P(s)that quantifies the likelihood that the two records represent the sameperson. If P(s) is greater than a predetermined threshold, the tworecords are provisionally determined to represent the same person. Thisprocess may be referred to as “individual correlation.”

Properly correlating all individual records theoretically requirescomparing every individual record to every other individual record. Thisprocess, however, quickly may become an overwhelming task given thepossible number of records. Thus, the process may be simplified in anyof a number of ways. In a specific example, individual correlation maybe simplified using, for example, a surname index to partition data intogroups based on surname. The comparison process may be furthersimplified using, for example, a sort on first name, birth date, orother relevant data within the individual record. The partitioningprocess will be explained in more detail hereinafter.

Following individual correlation, at block 208 those records that havebeen determined provisionally to represent the same person (i.e., “sameas records”) undergo “relationship correlation” as will be described. Ina specific example, the individual links records relating to the same asrecords are consulted to determine whether parent relationships existfor each. If so, the respective parent records are compared to oneanother, if the comparison was not previously completed duringindividual correlation. Each comparison results in a factor, P(f) thatrepresents a comparison of the father records, and a factor P(m) thatrepresents a comparison of the mother records. The P(s), P(f), and P(m)factors are then collectively used in the following formula to calculateP(s|f,m) representing a revised likelihood that the two same as recordsrelate to the same person:

${P\left( {{s❘f},m} \right)} = \frac{{P(f)}{P(m)}{P(s)}}{{{P(f)}{P(m)}{P(s)}} + {{P\left( f^{\prime} \right)}{P\left( m^{\prime} \right)}{P\left( s^{\prime} \right)}}}$Where P(s′)=1−P(s); P(f′)=1−P(f); and P(m′)=1−P(m). If P(s|f,m) exceedsa pre-determined threshold, then the two same as records are deemed torelate to the same person. This specific example of relationshipcorrelation is shown graphically in FIG. 2B. It is to be understood,however, that other algorithms are possible, including ones thatencompass more generations or work from ancestors to descendants, ratherthan from descendants to ancestors.

At block 210, records are consolidated into person pages. Person pagescomprise records of consolidated information about a person and mayinclude assertions, alternative assertions, relationships, alternativerelationships, sources of the information used to compile the personpage, and the like. This involves consolidating all information fromsame as records into a single person page, and creating a single personpage for unique records. One specific example of a person page 230 isillustrated in FIG. 2C.

At block 212, a request is received from a user to display a familytree. The request minimally includes a name of a person; however, inmost instances, at least one additional piece of information about theperson may be required. The additional piece of information may be anassertion about the person (e.g., birth, death, birthplace, death place,and the like).

At block 214, a file is constructed using the information provided inthe request. The file comprises assertions about the person identifiedby the requester, and a family tree using the person as the root. Theinformation is compiled by locating a person page relating to theperson, then using the person page to locate other person pages relatedto the person. Alternative relationships also may be included. The filealso may include scores relating to the likelihood that assertions andrelationships are correct. The scoring process for relationships wasdescribed above; assertions may be similarly scored. At block 216, thefile is sent to the user.

In some embodiments the user is given the opportunity to “drill down” tomore detailed information about someone or something in the file. Inresponse, the additional information is located and sent to the user. Insome embodiments, this information is located in the original personpage or a related person page. For example, the user may be able tonavigate up a family tree by selecting children of the root and having anew tree generated based on the child as a root. In other embodiments,responding to the request involves selecting information from therecords in the other data database. Many such examples are possible. Thedrill down process is shown as block 218.

In some embodiments the user is provided the option of selecting amongalternatives. If provided and the user does so, the tree may be updatedbased on the selected alternative. In some embodiments, the user'sselections are saved for the next time the user access the same tree.The iterative process of selecting and storing alternatives is shown inas block 220.

In some embodiments, the user is given the opportunity to provideinformation. The information may comprise one or more digital pictures,files of text (e.g., a journal of a person in the requested tree, or anote about what a user knows about the person or about the sources usedto evaluate information), and the like. This information may be madeavailable to other users. The user also may submit genealogy data.User-submitted genealogy data is received, stored, and processed asdescribed above. The receipt of user information is shown as block 222.

The foregoing process may be repeated periodically or continuously asnew data is received. In some embodiments, a records update processtakes place in batch mode. In other embodiments, the process takes placeeach time new data is submitted. In still other embodiments, the updateprocess is a combination of batch and continuous and may depend on thesource from which the data originates.

As new data is added to the system, probability factors relating toassertions about personas and links between personas may change. Thus, afamily tree originating from the same root and presented to a user onsubsequent visits may be different. This may be handled in a number ofways. In one embodiment, the user is presented with the new informationupon re-accessing the system. The user then may be presented with asummary of the changed inferences and given an opportunity to accept,partially accept or reject the resulting effect on the user's familytree. In other embodiments, the information shows up as an alternativeselection and the user may select among the alternatives. In still otherembodiments, the system generates a message, such as an email or a listof changes on a web page, that is sent to affected users when newcalculations are made that affect their trees. The options then may bepresented to affected users when they next access the system. Otherembodiments use a combination of the foregoing. The process of notifyingusers regarding updates is shown as block 224.

Those skilled in the art will appreciate that the software to implementthe method described above and any variation on it may be coded in mostany programming language. In a specific embodiment, however, XML isused. In other embodiments, however, XML is used to represent the data,the code to correlate and consolidate is written in JAVA and C++, andthe code to display the persona to the user are is written using HTML,JavaScript, and the .NET framework. Additionally, a relational databaseis used to manage the data at various points in the process. The codemay reside on one or more computing devices that cooperate to performthe methods described above.

Attention is directed to FIGS. 3A-3Q, which illustrate a more specificexample of the process of receiving, storing, and analyzing genealogydata. For example, FIGS. 3A and 3B depict data being received from theAncestry World Tree database. The data exists as one or more GEDCOMfiles 302. The data is read using a data extractor 304, which may bespecifically designed to extract data from a specific data storageenvironment. Through a data scrubbing process 306, the data is parsedand evaluated. This may involve assessing its completeness, accuracy, orother characteristics. Data whose utility or accuracy falls below apre-established threshold is rejected to an AWT threshold failed file308. The remaining data is stored in one or more records in specificdatabases. These include an individual nodes database 310, an individuallinks database 312, an other data database 314, and a surname index 316.The individual nodes database 310 stores individuals and core data(birth and death dates) as well as the source of the data. Theindividual links database 312 stores links between individuals and thetype of link. The other data database 314 stores information notcritical to the data evaluation and relationship analysis processes. Thesurname index 316 stores surnames and counts of surnames. Particularuses for each of the databases will be described in more detail below.FIG. 3B more clearly illustrates the placement of specific data fromGEDCOM files into records in these databases.

As shown in FIG. 3B, a unique record is created in several of thedatabases for an individual entry from a GEDCOM file. Names, birthdates,and deathdates for each individual go into records in the individualnodes database 310. Names, comments, and sources go into records in theother data database 314. Relationships types and the related individualnames go into records in the individual links database 312. Although notshown, surnames go into the surname index 316 along with a count of thenumber of records in which the surname exists.

FIGS. 3C and 3D illustrate a specific example of the process forextracting data from the AWT database. FIG. 3C shows three differentGEDCOM files 302. At this point, no conclusions are reached regardingwhether the individuals identified in the three different GEDCOM filesare related. As shown in FIG. 3D, each instance of a name results in aseparate record in the individual nodes database 310. Entries in therecords identify the source of the data (DB) and create a unique ID forthe data (ID). Other entries include name, birth, birth date, death, anddeath place. Of course, in other examples other data could be includedin the records. Each instance of a relationship among individualsresults in a record in the individual links database 312. Each recordincludes links that identify the source for the data (DB1, DB2), therecord identifier from the individual nodes database 310, and therelationship. Each unique surname results in a record in the surnameindex 316, and a record in the surname index counts the number ofoccurrences of the surname.

FIG. 3E illustrates a data extraction process for a census database(1930 US Federal Census). The data resides in census source files 320.The data is extracted using an extractor 322 that may be specificallydesigned for extracting census records. The data is then stored asrecords in an individual nodes database 324 relating to the census andas records in an individual links database 326, also relating to thecensus. Note that a data scrubbing process is not shown. It may be thecase that some source data is acceptable without scrubbing. The absenceof a surname index indicates that some source databases do notcontribute to surname counts.

FIGS. 3F and 3G illustrate a specific example of a data extractionprocess from a census database (e.g., the 1880 US Federal Census). FIG.3F illustrates data in a specific census record, and FIG. 3G illustratesthe placement of the resulting data in the individual nodes database 324and the individual links database 326.

FIG. 3H illustrates a data extraction process for data from a socialsecurity death index (SSDI-Social Security Death Index) database. Thedata exists in individual files 330 and is extracted using an extractionprocess 332 that may be unique to this database. The data is then parsedand stored in an individual nodes database 334. In this example, becausethe source does not include relationships, no entry results into anindividual links database. As was the case with the census databaseextraction process, no data scrubbing is used and no entries are made ina surname index.

It should be noted that the three data extraction examples justdescribed are merely exemplary. Many other such examples are possibleand apparent to those skilled in the art in light of this disclosure.

Continuing with the example, attention is directed to FIGS. 31 and 3J,which illustrate a process of correlating individual records. In thisprocess, individual records from each of several individual nodesdatabases 310, 324, 334, 342 are compared to each other using anindividual correlation function 344 to determine if the records relateto the same individual. Individual records whose data is identical ornearly identical when compared (i.e., individual correlation above athreshold) are stored in a same as nodes database 346 and are presumedto identify the same individual. As shown in FIG. 3J, the records in thesame as nodes database 346 include the person names and recordidentifiers for the related records as well as a score that representsthe degree to which the records are similar.

To simplify the comparison process, the individual records may bepartitioned into smaller groups. In this example, the surname index 316is used, together with a surname partition function 340 to partitiondata into manageable pieces. Because surnames for the same individualmay be spelled slightly differently, a phonetic algorithm such as doublemetaphone, SOUNDEX, and/or the like may be used to keep similar names inthe same partition even if they are spelled differently. The processthen may be further simplified by sorting a partition on, for example,first name, birth data and/or year or other relevant data. Recordswithin a partition and/or within ranges in the partition are compared toeach other, thus significantly reducing the total number of comparisonsthat must be made.

The individual correlation process discussed immediately above may failto identify records for individuals that completely changed their name.To avoid the problems this may cause, related records may undergoindividual correlation after relationship correlation. Thus, two recordsfor the same woman who changed her name at marriage may be identifiedonce her father is identified if, for example, her first name and birthdate are the same in the two records in which her last name isdifferent.

FIG. 3K illustrates a specific example of the individual correlationprocess using the AWT individual nodes database 310 and the censusindividual nodes database 324 created earlier in the example. Thecomparison based on surnames results in a correlated individuals list350. In this simplified example, the correlated individuals list 350only includes entries based on the name “John William Jefferson.” Fromthe individual nodes database 310, a comparison of NodeID 1 to NodeID 2results in an entry in the correlated individuals list 350 identified asCorr ID 1. The entry includes the source (DB1, DB2) and record ID (ID1,ID2) for the compared records and the score that the comparisongenerated. In the case of Corr ID 1, the comparison resulted in a scoreof 0.8. This is because the death place differs between NodeID 1 andNodeID 2 of the individual nodes database 310. A comparison betweenNodeID 2 and NodeID 3 from the same database, however, resulted in ascore of 1.0 as can be appreciated from Corr ID 3 in the correlatedindividuals list 350. The remaining entries in the correlatedindividuals list 350 result from other entries based on the name “JohnWilliam Jefferson.”

FIGS. 3L and 3M illustrate a further refinement of the correlationprocess based on relationships. The process once again uses the surnameindex 316 and a surname partition function 360 to evaluate data storedin the individual links databases 312, 326, 362. The data is extractedinto a relationship correlation function 364 and the records identifiedas being related to same as nodes are compared. The comparison updatesthe scores calculated previously in the individual correlation process.Thus, the scores in the same as nodes database 346 may be revised baseon the comparisons. FIG. 3N illustrates a continuation of the specificexample developed thus far.

FIG. 3N relates only to the record identified by Corr ID 1 in thecorrelated individuals list 350. The initial comparison duringindividual correlation of records ejerrer-I012 and a14243-I9571 resultedin a score of 0.8. Comparing the corresponding parent records for thesetwo records, however, results in a perfect match in both cases, a scoreof 1.0. This may be seen by returning to FIG. 3K and comparing NodeIDs 4and 5 and NodeIDs 7 and 8 of the individual nodes database 310. Thus,the score for Corr ID 1 of the correlated individuals list 350 may berevise upward to 1.0, representing a combination of the threecomparisons. Similar relationship comparisons are used to revise thescores for the remaining records.

FIGS. 3O and 3P illustrate a continuation of the process in whichrecords identified to be the same person are consolidated. Records fromthe individual nodes databases 370 (which may include the AWT individualnodes database 310) and records from the same as nodes database 346 areinput into an individual consolidation process 372. The output from theindividual consolidation process 372 is a record in a person pagesdatabase 374 for each group of related individual records. Thus, at theconclusion of the process, a person page exists for each group ofindividual records from a multitude of different sources, the recordsdetermined to have been related by calculating a score based on acomparison of the individual records then adjusting the score bycomparing records linked to the source records. If the score is above apre-determined threshold, then the records are presumed related. A finalconsolidation for “John William Jefferson” is illustrated in FIG. 3Q.

In FIG. 3Q, the records relating to “John William Jefferson” from thecorrelated individuals list 350 are condensed into a record in a personsdatabase 380. A person page 382 includes data from the source recordsand lists alternative information where comparisons did not result inperfect matches. The person page includes the relevant information fromthe original records in the individual nodes and the individual linksdatabases as well as the data sources. Some embodiments could alsoinclude scores for each assertion and relationship. As emphasizedpreviously, although some data may be disregarded for various reasonsbecause it does not exceed a threshold for accuracy or for otherreasons, no data is overwritten and therefore lost in the process. Auser performing a genealogical investigation is presented with a summaryof the most relevant data and may further evaluate its utility. The useris not forced to accept data that someone else has deemed accurate. Theuser may view alternate data to determine what he or she believes to bemost accurate. The user may also later change his or her mind and choosea different set of alternate information. No information is lost in anyof this analysis and choosing of data.

The foregoing example depicted in FIGS. 3A-3Q will be understood bythose skilled in the art to be non-limiting and merely illustrative of aprocess for receiving and parsing data from one or more data sources.Similar processes may operate to consolidate relationships and evenentire family trees, both of which are included within the scope ofembodiments of the present invention and the claims that follow.

Attention is directed to FIGS. 4A-4D, which illustrate a series ofscreen displays that depict a user interface from a user computer to thehost computer system. FIG. 4A depicts a first display screen 400 showingancestry information about “Ruth Pabodie,” the person selected foranalysis by the user. The display screen 400, as with the displayscreens to be described hereinafter, may be displayed for the user in abrowser environment, for example. In another example, the displayscreens may be generated by client software operating on the user'scomputer. Many other examples are possible. The display screen 400includes a personal information area 402 listing information about theroot person such as birth and death information, spouses, and children.Conveniently, listed information may serve as a hyperlink to moredetailed information. The display screen also includes a family tree404. The family tree depicted in this display screen 400 goes back threegenerations from the root person, listing Ruth Pabodie's parents,grandparents, and great grandparents. Each person in the tree may beselectable as a hyperlink. An additional information section 406provides hyperlinks to other resources relevant to the root person. Thismay include user-submitted information, source records, newspapers fromthe root person's birth and death dates, and the like.

In some embodiments, attention symbols 408 are used to indicate thepresence of alternatives relating to the information marked by theattention symbol. In this example, Ruth Pabodie's father is marked by aattention symbol 408. By selecting the attention symbol 408 next toRuth's father, the user is presented with the display screen 410 of FIG.4B.

The display screen 410 of FIG. 4B includes an alternative fatherselection area 412 having three alternatives. In this example, threerecords were found that could be related to Ruth as her father. Ratherthan force the user into using the most likely alternative (the onemarked with an asterisk 414), this embodiment of the present inventionallows the user to view the data and make a selection using the selectbuttons 416. Once the user has made the selection, or if the userchooses not to make a selection, the user may select a done button 418to return to the previous display screen 400. FIG. 4C illustrates asimilar display screen 420 for selecting among alternative birth recordsfor Ruth Pabodie. This process was described above with reference toblock 220 of FIG. 2. In some embodiments, a different symbol replacesthe attention symbol 408 to indicate that the user has chosen amongalternatives.

Users may also view the records associated to each of the conflictingdata references by clicking on a hyperlinked number or list of sourcedocument types to view the records or sources which provided theconflicting data. This will better inform the user where the informationcame from and allow them to make a more informed decision about whichconflicting data may be correct. Users' choices of which alternativedata they believe to be correct may also be logged in the system asvotes. These votes may then be tallied and used to inform the system ofwhich choice users thought was more likely correct. This voting may thenbe used to change which piece of alternative data the system believes tobe most likely.

As described above with reference to block 224 of FIG. 2, if newinformation changes inferences prior to a subsequent visit by the user,attention symbols 408 may appear in new places and/or replace symbolsshowing that the user has selected among alternatives.

Attention symbols may also be used to denote which nodes have newmessages, comments, pictures, stories, or other new or modified data.Attention symbols may also be used to help a user locate nodes which aremissing key data such as birth date, death place, etc.

Returning to FIG. 4A, a details link 422 allows the user to drill downinto more detail information about a subject, in this case Ruth'spersonal information. By doing so, the user is presented with thedisplay screen 424 of FIG. 4D. This process was described in more detailwith respect to block 218 of FIG. 2.

Returning to FIG. 4A, the absence of specific information for a rootperson may be indicated with brackets 426, as is the case for the dayand month that Ruth Pabodie married.

The foregoing display screens are merely exemplary of display screensthat may be used in connection with embodiments of the invention. Otherembodiments may include more, fewer, or different display screens, as isapparent to those skilled in the are in light of this disclosure.

Having described several embodiments, it will be recognized by those ofskill in the art that various modifications, alternative constructions,and equivalents may be used without departing from the spirit of theinvention. Additionally, a number of well known processes and elementshave not been described in order to avoid unnecessarily obscuring thepresent invention. For example, those skilled in the art know how toarrange computers into a network and enable communication among thecomputers. Accordingly, the above description should not be taken aslimiting the scope of the invention, which is defined in the followingclaims.

1. A method of consolidating genealogy records, comprising: partitioningthe records using at least one index file to form one or morepartitions, wherein each record represents an individual and includes aname data element and at least one additional data element selected froma group of data elements consisting of birth date, birth place, deathdate, and death place, and wherein each record has links associatedtherewith, wherein the links identify related records representing anindividual related to the individual of the record; sorting the recordsin a partition based on a data element in the records; comparing recordswithin a sort range; based on the comparison, identifying same personrecords, wherein identifying same person records comprises: calculatinga factor that represents the likelihood that two records represent thesame individual; comparing the factor to a predetermined threshold;based on the comparison, provisionally determining whether the recordsrepresent the same individual; for each pair of records provisionallydetermined to represent the same individual: calculating a factor thatrepresents the likelihood that respective mother records for the pair ofrecords represent the same mother; calculating a factor that representsthe likelihood that respective father records for the pair of recordsrepresent the same father; using the factor that represents thelikelihood that the two records represent the same individual, thefactor that represents the likelihood that respective mother records forthe pair of records represent the same mother, and the factor thatrepresents the likelihood that respective father records for the pair ofrecords represent the same father, calculating a revised factorrepresenting the likelihood that the pair of records represent the sameindividual; comparing the revised factor to a predetermined threshold;and based on the comparison, determining that the two records representthe same individual; consolidating information in the same personrecords; receiving a request from a user to view at least a portion ofthe consolidated information for a particular group of same personrecords; and sending a file comprising the portion to the user.
 2. Themethod of claim 1, wherein partitioning the records using at least oneindex file comprises using a surname index to identify records havingthe same surnames and grouping those records into a surname partition.3. The method of claim 2, further comprising using the surname index toidentify records having similar surnames and grouping those records intothe surname partition.
 4. The method of claim 3, wherein using thesurname index to identify records having similar surnames comprisesusing a phonetic algorithm to identify records having similar surnames.5. The method of claim 4, wherein the phonetic algorithm comprisesdouble metaphone.
 6. The method of claim 4, wherein the phoneticalgorithm comprises SOUNDEX.
 7. The method of claim 1, wherein sortingthe records in a partition based on a data element in the recordscomprises sorting the records based on birth date.
 8. The method ofclaim 1, wherein sorting the records in a partition based on a dataelement in the records comprises sorting the records based on aselection from the group consisting of name, death data, death place,and birth place.
 9. The method of claim 1, wherein the portion comprisesa family tree based on consolidated information from a plurality ofrecords.
 10. A system for consolidating genealogy records, comprising: aprocessor programmed to: partition the records using at least one indexfile to form one or more partitions, wherein each record represents anindividual and includes a name data element and at least one additionaldata element selected from a group of data elements consisting of birthdate, birth place, death date, and death place, and wherein each recordhas links associated therewith, wherein the links identify relatedrecords representing an individual related to the individual of therecord; sort the records in a partition based on a data element in therecords; compare records within a sort range; based on the comparison,identify same person records, by: calculating a factor that representsthe likelihood that two records represent the same individual; comparingthe factor to a predetermined threshold; based on the comparison,provisionally determining whether the records represent the sameindividual; for each pair of records provisionally determined torepresent the same individual: calculating a factor that represents thelikelihood that respective mother records for the pair of recordsrepresent the same mother; calculating a factor that represents thelikelihood that respective father records for the pair of recordsrepresent the same father; using the factor that represents thelikelihood that the two records represent the same individual, thefactor that represents the likelihood that respective mother records forthe pair of records represent the same mother, and the factor thatrepresents the likelihood that respective father records for the pair ofrecords represent the same father, calculating a revised factorrepresenting the likelihood that the pair of records represent the sameindividual; comparing the revised factor to a predetermined threshold;and based on the comparison, determining that the two records representthe same individual; consolidate information in the same person records;receive a request from a user to view at least a portion of theconsolidated information for a particular group of same person records;and send a file comprising the portion to the user.
 11. The system ofclaim 10, wherein the processor, in being programmed to partition therecords using at least one index file is further programmed to use asurname index to identify records having the same surnames and groupingthose records into a surname partition.
 12. The system of claim 11, theprocessor is further programmed to use the surname index to identifyrecords having similar surnames and group those records into the surnamepartition.
 13. The system of claim 12, wherein the processor, in beingprogrammed to use the surname index to identify records having similarsurnames is further programmed to use a phonetic algorithm to identifyrecords having similar surnames.
 14. The system of claim 13, wherein thephonetic algorithm comprises double metaphone.
 15. The system of claim13, wherein the phonetic algorithm comprises SOUNDEX.
 16. The system ofclaim 10, wherein the processor, in being programmed to sort the recordsin a partition based on a data element in the records is furtherprogrammed to sort the records based on birth date.
 17. The system ofclaim 10, wherein the processor, in being programmed to sort the recordsin a partition based on a data element in the records is furtherprogrammed to sort the records based on a selection from the groupconsisting of name, death data, death place, and birth place.
 18. Thesystem of claim 16, wherein the processor, in being programmed tocompare records within a sort window is further programmed to comparerecords within a birth date range.
 19. The system of claim 10, whereinthe portion comprises a family tree based on consolidated informationfrom a plurality of records.
 20. A method of consolidating genealogyrecords, comprising: partitioning the records using at least one indexfile to form one or more partitions, wherein each record represents anindividual and includes a name data element and at least one additionaldata element selected from a group of data elements consisting of birthdate, birth place, death date, and death place, and wherein each recordhas links associated therewith, wherein the links identify relatedrecords representing an individual related to the individual of therecord; sorting the records in a partition based on a data element inthe records, wherein sorting the records in a partition based on a dataelement in the records comprises sorting the records based on birthdate; comparing records within a sort range, wherein comparing recordswithin a sort range comprises comparing records within a birth daterange; based on the comparison, identifying same person records, whereinidentifying same person records comprises: calculating a factor thatrepresents the likelihood that two records represent the sameindividual; comparing the factor to a predetermined threshold; based onthe comparison, provisionally determining whether the records representthe same individual; for each pair of records provisionally determinedto represent the same individual: calculating a factor that representsthe likelihood that respective mother records for the pair of recordsrepresent the same mother; calculating a factor that represents thelikelihood that respective father records for the pair of recordsrepresent the same father; using the factor that represents thelikelihood that the two records represent the same individual, thefactor that represents the likelihood that respective mother records forthe pair of records represent the same mother, and the factor thatrepresents the likelihood that respective father records for the pair ofrecords represent the same father, calculating a revised factorrepresenting the likelihood that the pair of records represent the sameindividual; comparing the revised factor to a predetermined threshold;and based on the comparison, determining that the two records representthe same individual; consolidating information in the same personrecords; receiving a request from a user to view at least a portion ofthe consolidated information for a particular group of same personrecords; and sending a file comprising the portion to the user.